Linkable issue queue parallel execution slice processing method

ABSTRACT

A method of processing using an execution slice circuit including multiple parallel instruction execution slices provides flexible and efficient use of internal resources. The execution slice circuit includes a master execution slice for receiving instructions of a first instruction stream and a slave execution slice for receiving instructions of a second instruction stream and instructions of the first instruction stream that require an execution width greater than a width of the slices. The method also detects when a first instruction of the first instruction stream has the greater width and controls the slave execution slice to reserve a first issue cycle for issuing the first instruction in parallel across the master execution slice and the slave execution slice.

The present application is a Continuation of U.S. patent application Ser. No. 14/595,549, filed on Jan. 13, 2015 and claims priority thereto under 35 U.S.C. §120. The disclosure of the above-referenced parent U.S. patent application is incorporated herein by reference.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention is related to processing systems and processors, and more specifically to a pipelined processor core with reconfigurable architecture in which a parallel execution slice issue queue is linked for executing instructions of differing width.

2. Description of Related Art

In present-day processor cores, pipelines are used to execute multiple hardware threads corresponding to multiple instruction streams so that more efficient use of processor resources can be provided through resource sharing, and by allowing execution to proceed even while one or more hardware threads are waiting on an event.

Typical execution pipelines are set up to execute instructions of fixed width, or to execute portions of vector instructions in parallel, since the control logic to manage the execution of instructions is typically fixed. Such architectures are constrained to their fixed instruction execution architecture and when a parallel processor is executing non-vector instructions, processor resources are typically not being used.

It would therefore be desirable to provide a method for processing program instructions that provides improved use of the processor core resources.

BRIEF SUMMARY OF THE INVENTION

The invention is embodied in a method of processing using an execution slice circuit. The method is a method of operation of a processor core.

The method uses an execution slice circuit including multiple parallel instruction execution slices for executing multiple instruction streams including a master execution slice for receiving instructions of a first instruction stream, and a slave execution slice for receiving instructions of a second instruction stream and instructions of the first instruction stream that require an execution width greater than a width of the slices. The execution slice circuit also detects when a first instruction of the first instruction stream has the greater width and controls the slave execution slice to reserve a first issue cycle for issuing the first instruction in parallel across the master execution slice and the slave execution slice.

The foregoing and other objectives, features, and advantages of the invention will be apparent from the following, more particular, description of the preferred embodiment of the invention, as illustrated in the accompanying drawings.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWING

The novel features believed characteristic of the invention are set forth in the appended claims. The invention itself, however, as well as a preferred mode of use, further objectives, and advantages thereof, will best be understood by reference to the following detailed description of the invention when read in conjunction with the accompanying Figures, wherein like reference numerals indicate like components, and:

FIG. 1 is a block diagram illustrating a processing system in which techniques according to an embodiment of the present invention are practiced.

FIG. 2 is a block diagram illustrating details of a processor core 20 that can be used to implement processor cores 20A-20B of FIG. 1.

FIG. 3 is a pictorial diagram illustrating configuration of processor core 20 in particular operating modes.

FIG. 4 is a block diagram illustrating details of processor core 20.

FIG. 5 is a control flow diagram illustrating an exemplary control flow that may be implemented within processor core 20.

FIG. 6 is a flowchart illustrating a method of operation of processor core 20.

FIG. 7 is a block diagram illustrating details of an instruction execution slice 42AA that can be used to implement instruction execution slices ES0-ES7 of FIGS. 2-3.

FIG. 8 is a block diagram illustrating details within an exemplary embodiment of an execution interlock control logic 79 of FIG. 7.

FIG. 9 is a block diagram illustrating details of a cache slice 44 that can be used to implement load-store slices LS0-LS7 of FIGS. 2-3.

DETAILED DESCRIPTION OF THE INVENTION

The present invention relates to processors and processing systems in which conventional pipelines are replaced with execution slices that can be reconfigured to efficiently allocate subsets of resources based on one or more thread mode control signals that may select between single-threaded mode, multi-threaded mode and different numbers of simultaneously executing hardware threads. In particular, the processor described below includes execution slices that are paired as master/slave slices with control logic to permit execution of instructions requiring greater width than a base width of the slices by joining two slices when a wider instruction is dispatched to the slices.

Referring now to FIG. 1, a processing system in accordance with an embodiment of the present invention is shown. The depicted processing system includes a number of processors 10A-10D, each in conformity with an embodiment of the present invention. The depicted multi-processing system is illustrative, and a processing system in accordance with other embodiments of the present invention include uni-processor systems having multi-threaded cores. Processors 10A-10D are identical in structure and include cores 20A-20B and a local storage 12, which may be a cache level, or a level of internal system memory. Processors 10A-10D are coupled to a main system memory 14, a storage subsystem 16, which includes non-removable drives and optical drives, for reading media such as a CD-ROM 17 forming a computer program product and containing program instructions implementing generally, at least one operating system, associated applications programs, and optionally a hypervisor for controlling multiple operating systems' partitions for execution by processors 10A-10D. The illustrated processing system also includes input/output (I/O) interfaces and devices 18 such as mice and keyboards for receiving user input and graphical displays for displaying information. While the system of FIG. 1 is used to provide an illustration of a system in which the processor architecture of the present invention is implemented, it is understood that the depicted architecture is not limiting and is intended to provide an example of a suitable computer system in which the techniques of the present invention are applied.

Referring now to FIG. 2, details of an exemplary processor core 20 that can be used to implement processor cores 20A-20B of FIG. 1 are illustrated. Processor core 20 includes an instruction cache (ICache) 54 and instruction buffer (IBUF) 31 that store multiple instruction streams fetched from cache or system memory and present the instruction stream(s) via a bus 32 to a plurality of dispatch queues Disp0-Disp7 within each of two clusters CLA and CLB. Control logic within processor core 20 controls the dispatch of instructions from dispatch queues Disp0-Disp7 to a plurality of instruction execution slices ES0-ES7 via a dispatch routing network 36 that permits instructions from any of dispatch queues Disp0-Disp7 to any of instruction execution slices ES0-ES7 in either of clusters CLA and CLB, although complete cross-point routing, i.e., routing from any dispatch queue to any slice is not a requirement of the invention. In certain configurations as described below, the dispatch of instructions from dispatch queues Disp0-Disp3 in cluster CLA will be restricted to execution slices ES0-ES3 in cluster CLA, and similarly the dispatch of instructions from dispatch queues Disp4-Disp7 in cluster CLB will be restricted to execution slices ES4-ES7. Instruction execution slices ES0-ES7 perform sequencing and execution of logical, mathematical and other operations as needed to perform the execution cycle portion of instruction cycles for instructions in the instruction streams, and may be identical general-purpose instruction execution slices ES0-ES7, or processor core 20 may include special-purpose execution slices ES0-ES7. Other special-purpose units such as cryptographic processors 34A-34B, decimal floating points units (DFU) 33A-33B and separate branch execution units (BRU) 35A-35B may also be included to free general-purpose execution slices ES0-ES7 for performing other tasks. Instruction execution slices ES0-ES7 may include multiple internal pipelines for executing multiple instructions and/or portions of instructions.

The load-store portion of the instruction execution cycle, (i.e., the operations performed to maintain cache consistency as opposed to internal register reads/writes), is performed by a plurality of load-store (LS) slices LS0-LS7, which manage load and store operations as between instruction execution slices ES0-ES7 and a cache memory formed by a plurality of cache slices CS0-CS7 which are partitions of a lowest-order cache memory. Cache slices CS0-CS3 are assigned to partition CLA and cache slices CS4-CS7 are assigned to partition CLB in the depicted embodiment and each of load-store slices LS0-LS7 manages access to a corresponding one of the cache slices CS0-CS7 via a corresponding one of dedicated memory buses 40. In other embodiments, there may be not be a fixed partitioning of the cache, and individual cache slices CS0-CS7 or sub-groups of the entire set of cache slices may be coupled to more than one of load-store slices LS0-LS7 by implementing memory buses 40 as a shared memory bus or buses. Load-store slices LS0-LS7 are coupled to instruction execution slices ES0-ES7 by a write-back (result) routing network 37 for returning result data from corresponding cache slices CS0-CS7, such as in response to load operations. Write-back routing network 37 also provides communications of write-back results between instruction execution slices ES0-ES7. An address generating (AGEN) bus 38 and a store data bus 39 provide communications for load and store operations to be communicated to load-store slices LS0-LS7. For example, AGEN bus 38 and store data bus 39 convey store operations that are eventually written to one of cache slices CS0-CS7 via one of memory buses 40 or to a location in a higher-ordered level of the memory hierarchy to which cache slices CS0-CS7 are coupled via an I/O bus 41, unless the store operation is flushed or invalidated. Load operations that miss one of cache slices CS0-CS7 after being issued to the particular cache slice CS0-CS7 by one of load-store slices LS0-LS7 are satisfied over I/O bus 41 by loading the requested value into the particular cache slice CS0-CS7 or directly through cache slice CS0-CS7 and memory bus 40 to the load-store slice LS0-LS7 that issued the request. In the depicted embodiment, any of load-store slices LS0-LS7 can be used to perform a load-store operation portion of an instruction for any of instruction execution slices ES0-ES7, but that is not a requirement of the invention. Further, in some embodiments, the determination of which of cache slices CS0-CS7 will perform a given load-store operation may be made based upon the operand address of the load-store operation together with the operand width and the assignment of the addressable byte of the cache to each of cache slices CS0-CS7.

Instruction execution slices ES0-ES7 may issue internal instructions concurrently to multiple pipelines, e.g., an instruction execution slice may simultaneously perform an execution operation and a load/store operation and/or may execute multiple arithmetic or logical operations using multiple internal pipelines. The internal pipelines may be identical, or may be of discrete types, such as floating-point, scalar, load/store, etc. Further, a given execution slice may have more than one port connection to write-back routing network 37, for example, a port connection may be dedicated to load-store connections to load-store slices LS0-LS7, or may provide the function of AGEN bus 38 and/or data bus 39, while another port may be used to communicate values to and from other slices, such as special-purposes slices, or other instruction execution slices. Write-back results are scheduled from the various internal pipelines of instruction execution slices ES0-ES7 to write-back port(s) that connect instruction execution slices ES0-ES7 to write-back routing network 37. Cache slices CS0-CS7 are coupled to a next higher-order level of cache or system memory via I/O bus 41 that may be integrated within, or external to, processor core 20. While the illustrated example shows a matching number of load-store slices LS0-LS7 and execution slices ES0-ES7, in practice, a different number of each type of slice can be provided according to resource needs for a particular implementation.

Within processor core 20, an instruction sequencer unit (ISU) 30 includes an instruction flow and network control block 57 that controls dispatch routing network 36, write-back routing network 37, AGEN bus 38 and store data bus 39. Network control block 57 also coordinates the operation of execution slices ES0-ES7 and load-store slices LS0-LS7 with the dispatch of instructions from dispatch queues Disp0-Disp7. In particular, instruction flow and network control block 57 selects between configurations of execution slices ES0-ES7 and load-store slices LS0-LS7 within processor core 20 according to one or more mode control signals that allocate the use of execution slices ES0-ES7 and load-store slices LS0-LS7 by a single thread in one or more single-threaded (ST) modes, and multiple threads in one or more multi-threaded (MT) modes, which may be simultaneous multi-threaded (SMT) modes. For example, in the configuration shown in FIG. 2, cluster CLA may be allocated to one or more hardware threads forming a first thread set in SMT mode so that dispatch queues Disp0-Disp3 only receive instructions of instruction streams for the first thread set, execution slices ES0-ES3 and load-store slices LS0-LS3 only perform operations for the first thread set and cache slices CS0-CS3 form a combined cache memory that only contains values accessed by the first thread set. Similarly, in such an operating mode, cluster CLB is allocated to a second hardware thread set and dispatch queues Disp4-Disp7 only receive instructions of instruction streams for the second thread set, execution slices ES4-ES7 and LS slices LS4-LS7 only perform operations for the second thread set and cache slices CS4-CS7 only contain values accessed by the second thread set. When communication is not required across clusters, write-back routing network 37 can be partitioned by disabling transceivers or switches sw connecting the portions of write-back routing network 37, cluster CLA and cluster CLB. Separating the portions of write-back routing network 37 provides greater throughput within each cluster and allows the portions of write-back routing network 37 to provide separate simultaneous routes for results from execution slices ES0-ES7 and LS slices LS0-LS7 for the same number of wires in write-back routing network 37. Thus, twice as many transactions can be supported on the divided write-back routing network 37 when switches sw are open. Other embodiments of the invention may sub-divide the sets of dispatch queues Disp0-Disp7, execution slices ES0-ES7, LS slices LS0-LS7 and cache slices CS0-CS7, such that a number of clusters are formed, each operating on a particular set of hardware threads. Similarly, the threads within a set may be further partitioned into subsets and assigned to particular ones of dispatch queues Disp0-Disp7, execution slices ES0-ES7, LS slices LS0-LS7 and cache slices CS0-CS7. However, the partitioning is not required to extend across all of the resources listed above. For example, clusters CLA and CLB might be assigned to two different hardware thread sets, and execution slices ES0-ES2 and LS slices LS0-LS1 assigned to a first subset of the first hardware thread set, while execution slice ES3 and LS slices LS2-LS3 are assigned to a second subject of the first hardware thread set, while cache slices CS0-CS3 are shared by all threads within the first hardware thread set. In a particular embodiment according to the above example, switches may be included to further partition write back routing network 37 between execution slices ES0-ES7 such that connections between sub-groups of execution slices ES0-ES7 that are assigned to different thread sets are isolated to increase the number of transactions that can be processed within each sub-group. The above is an example of the flexibility of resource assignment provided by the bus-coupled slice architecture depicted in FIG. 2, and is not a limitation as to any particular configurations that might be supported for mapping sets of threads or individual threads to resources such as dispatch queues Disp0-Disp7, execution slices ES0-ES7, LS slices LS0-LS7 and cache slices CS0-CS7.

In another configuration, according to another state of the mode control signal(s), clusters CLA and CLB are configured to execute instructions for a common pool of threads, or for a single thread in an ST mode. In such a configuration, cache slices CS0-CS7 may be joined to form a larger cache that is accessible by instructions dispatched to any of execution slices ES0-ES7 via any of load-store slices LS0-LS7. Cache slices CS0-CS7 may be organized into a partitioned cache, for example by using the operand address of each cache operation to determine which of cache slices CS0-CS7 or sub-groups of cache slices CS0-CS7 should support an operation. For example, cache lines may be split across sub-groups of cache slices CS0-CS3 and CS4-CS7, such that a particular bit of the operand address selects which of the two groups of cache slices CS0-CS3 and CS4-CS7 will contain the specified value, forming an interleave of cache lines. For example, cache slices CS0-CS3 may store data values having odd cache line addresses and cache slices CS4-CS7 may store data values having even cache line addresses. In such a configuration, the number of unique cache lines addresses indexed within the cache may be held constant when selecting between modes in which the cache slices CS0-CS7 are partitioned among sets of threads and modes in which cache slices CS0-CS7 are joined. In another example, data may be “striped” across cache slices CS0-CS7 using three bits of the operand address to determine a target one of cache slices CS0-CS7, forming an interleave with a factor of 8. The above-illustrated examples are not exhaustive, and there are many different ways to assign data values to particular ones of cache slices CS0-CS7. For example, certain block or vector operations may deterministically span cache slices CS0-CS7 or sub-groups thereof, permitting early-decode-based assignment to one of execution slices ES0-ES7 or as among clusters CLA or CLB. Dispatch queues Disp0-Disp7 and/or execution slices ES0-ES7 may determine the appropriate target one (or more) of cache slices CS0-CS7 for an operation based on the operation type, address generation, a prediction structure, or other mechanisms. In one such exemplary embodiment of an operating mode, operations having odd operand addresses will be identified for processing on load-store slices LS0-LS3 only and cache slices CS0-CS3 are joined to only contain values representing odd addresses. Similarly, in such an exemplary embodiment of an operating mode, operations having even operand addresses are identified for processing by load-store slices LS4-LS7 only and cache slices CS4-CS7 only contain values representing even addresses. In the above-described configuration, cache slices CS0-CS7 may be conceptually joined, however, certain implementations such as vector or cache block operations do not require a full cross-bar routing between all load-store slices LS4-LS7, execution slices ES0-ES7 and cache slices CS0-CS7. In other configurations according to other modes, and/or in other embodiments of the invention, cache slices CS0-CS7 may be further partitioned to support SMT operations with four, eight, etc., independent partitions available to pools of hardware threads, as the illustrated embodiment having eight execution slices, eight load-store slices and eight cache slices is only illustrative and larger numbers of slices or clusters may be present in other embodiments of the invention.

Referring now to FIG. 3, an example of another configuration feature implemented within processor 20 is illustrated. In FIG. 3 execution slices ES0 and ES1 have been linked as a “super-slice” for executing an instruction that has operand width and/or operator width twice the width of instructions that are handled by execution slices ES0 and ES1 individually. For example, execution slices ES0 and ES1 may have 64-bit width and may be combined in a 128-bit super-slice according to the state of a mode control signal. Such a configuration may be used for executing instructions having, for example, operands in vector pairs that are processed by the same instruction. Alternatively, or in combination, the operator may be a wider operator or may contain immediate fields requiring the extra width. The super-slice configuration is not limited to pairs of execution slices. For example, three or more of execution slices ES0-ES7 might be linkable to provide a still wider operand and/or operator handling. For the wider 128-bit wide operations, dispatch queues such as Disp0 and Disp1 may also be joined. Alternatively, wider operations may be dispatch routed from a single one of dispatch queues Disp0-Disp7 to more than one of execution slice ES0-ES7 over dispatch routing network 36. In such an embodiment, if a super-slice is not available to execute a wider operation, the wider operation may be blocked from dispatch and maybe retained in the dispatch queue until a super-slice is available. Operations for other hardware threads that share the same dispatch queue can continue to be dispatched. Some wide operations, such as vector operations that do not require concurrent execution of each element of the vector, may be executed by a single execution slice, or a disjoint set of execution slices without requiring availability of a super-slice. Further details of control logic to manage formation of a super-slice for executing a wide instruction will be described in further detail below, with reference to FIGS. 5-6 and FIG. 8.

Referring now to FIG. 4, further details of processor core 20 are illustrated. Processor core 20 includes a branch execution unit 52, an instruction fetch unit (IFetch) 53 and instruction sequencer unit (ISU) 30 that control the fetching and sequencing of instructions. An input instruction buffer (IB) 51 buffers instructions in order to map the groups of instructions according to the execution slice resources allocated for the various threads and any super-slice configurations that are set, such as enabling pairs of slices to operate as master/slave slices as described below with reference to FIGS. 5-6 and FIG. 8. Another instruction buffer (IBUF) 31 is partitioned to maintain dispatch queues (Disp0-Disp7 of FIGS. 2-3) for each of the instruction streams and dispatch routing network 32 couples IBUF 31 to the segmented execution and load-store slices 50, which are coupled to cache slices 46. Instruction flow and network control block 57 performs control of segmented execution and load-store slices 50, cache slices 46 and dispatch routing network 32 to configure the slices as illustrated in FIGS. 2-3, according to a mode control/thread control logic 59. An instruction completion unit 58 is also provided to track completion of instructions sequenced by ISU 30 and to control write-back operations by load-store slices within segmented execution and load-store slices 50. A power management unit 56 may also provide for energy conservation by reducing or increasing a number of active slices within segmented execution and cache slices 50. Although instruction flow and network control block 57 is shown as a single unit, control of segmented execution within and between execution slices ES0-ES7 and load store slices LS0-LS7 may be partitioned among the slices such that each of execution slices ES0-ES7 and load store slices LS0-LS7 may control its own execution flow and sequencing while communicating with other slices.

Referring now to FIG. 5, a control flow diagram shows the process from dispatch through issue of a wide instruction or a pair of instructions within a master/slave pair of execution slices. As mentioned above, execution slices ES0-ES7 may perform a load/store operation and another operation such as fixed point (FX) or vector/scalar (VS) instruction. The control logic flow for the master execution slice is shown in the left portion of FIG. 5 and the control logic flow for the slave execution slice is shown in the right portion of FIG. 5. A load/store dispatch cycle and another operation cycle such as an FX dispatch are initiated in the master execution slice, and the oldest allowed instruction, as indicated by an allow vector AllowM is accessed by accessing age array 92A with allow vector AllowM. Operations dispatched to the master execution slice are written into reservation station 94A indexed by an age array 92A of the master execution slice issue queue and the operations for the slave execution slice are written into a reservation station 94B indexed by an age array 92B of the slave execution slice issue queue. Age arrays 92A, 92B maintain information on the order in which the operations were dispatched, so that once conditions are cleared for operations in reservation station 94A or 94B, the oldest such operation can be retrieved and issued. Age array 92A returns the oldest entry for which the corresponding bit is set in allow vector AllowM, and the entry provides an index/address into reservation station 94A, which issues the operation into master slice FX operand latch FXMop. An oldest LS operation can also be issued to LS operand latch LSMop from reservation station 94A in the same cycle via a separate look-up in age array 92A. Similarly, Age array 92B returns the oldest entry for which the corresponding bit is set in allow vector AllowS, and the entry provides an index/address into reservation station 94B, which issues the operation into slave slice FX operand latch FXSop. An oldest LS operation can also be issued to LS operand latch LSSop from reservation station 94B in the same cycle via a separate look-up in age array 92B. One LS operation and one FX/VS operation can be issued per cycle, per slice, or in the case of 128-bit wide FX/VS operations, one issue per cycle across both the master and slave execution slices.

If a wide operation is dispatched, which for the exemplary illustrations herein is a 128-bit operation to be performed by 64-bit execution slices, the halves of the 128-bit operation are dispatched to the master execution slice and slave execution slice, but may be indexed by different entries from age arrays 92A-92B. In order to keep track of the half of the 128-bit operation that is indexed by an entry in age array 92B of the slave execution slice, a queue position array (Qpos) 93 is provided in the master execution slice. When half of the 128-bit operation is written to age array 92B in the slave execution slice, a pointer/index to that location is stored in queue position array 93, which is indexed by an index retrieved from age array 92A. The wide (128-bit) operation is dispatched by writing the respective halves of the operation code to reservation stations 94A, 94B and generating entries in age arrays 92A, 92B. A bit is set in a latch 128 b that corresponds to the entry in age array 92A to indicate that the entry is part of a 128-bit (wide) operation. On each issue cycle, in addition to issuing the oldest allowed entry in each slice, a look-up is performed to determine whether the oldest ready entry is a 128-bit (wide) operation by comparing the oldest ready entry with the bit mask in latch 128 b illustrated as logical-AND operator AND1. The result of the comparison selects between the output of a 128-bit ready logic 128 b Ready and the output of a 64-bit ready logic 64 b Ready illustrated by multiplexer 91A. The output of multiplexer 91A is used to set the allow bits in allow vector AllowM for the next issue cycle. At the same time, the next issue cycle is reserved in the slave execution slice, so that both halves of the 128-bit operation can be issued in the same cycle.

In the particular embodiment illustrated herein, the reservation of an issue cycle in the slave execution slice is made at the time that the 128-bit operation becomes the oldest ready operation. As mentioned above, at each issue cycle, the master execution slice reads the oldest entry in age array 92A that has a ready flag that is set. Irrespective of whether the oldest entry in age array 92A corresponds to a 128-bit operation, the oldest allowed entries are issued at both the master and slave execution slices during the current issue cycle, which may be a 64-bit operation or a 128-bit operation. For the next operation issued, if the oldest ready entry in age array 92A corresponds to a 128-bit entry, the output of age array 92A corresponding to that entry is used to retrieve the half of the 128-bit operation indexed by an entry in age array 92B using the queue position array 93 and multiplexer 91B selects the output of queue position array 93 rather than the set of ready 64-bit operations in slave ready latch Rdy. The selected value updates the slave allow latch AllowS, so that on the next issue cycle, the half of the 128-bit operation will be retrieved from reservation station 94B using the index/address provided from queue position array 93. Otherwise, if the next operation to be issued is not a 128-bit operation, slave allow latch AllowS is updated from slave ready latch Rdy, so that the oldest 64-bit operation will be retrieved from reservation station 94B via the index/address of the oldest ready entry in age array 92B. Irrespective of whether two 64-bit FX/VS or a single 128-bit FX/VS operation is issued in an issue cycle, two 64-bit load-store operations are issued from reservation stations 94A and 94B at each issue cycle, unless there are other conditions not yet met, such as a lack of load-store dispatch entries, a lack of operations having ready conditions met, etc.

Referring now to FIG. 6, a method of controlling a master/slave pair of execution slices to issue wide instructions is shown. At each issue cycle, the oldest FX/VS operation having the allow bit set is selected for issue (step 60) from both the master and slave execution slices. The oldest allowed operation(s) are issued across both master and slave execution slices, which may be two separate 64-bit operations or a 128-bit operation issued by the master and slave execution slices acting as a superslice (step 61). At the same time, the entry for the oldest ready FX/VS operation is retrieved from the age array in the master slice (step 62). If the entry corresponds to a 128-bit FX/VS operation (decision 63), then the allow bit(s) are set for all ready 128-bit operations in the allow vector (step 64) and the queue position array entry corresponding to the 128-bit operation is selected and used to set the allow vector for the slave execution slice so that the bit corresponding to the other half of the 128-bit entry is set in the allow vector (step 65). After setting the allow vector, the ready bit for that entry is cleared (step 67), to prevent subsequent re-load of the entry that is being set up for issue on the next issue cycle, and until the system or scheme is shut down (step 68), the next issue cycle commences by repeating steps 60-69.

Referring now to FIG. 7, an example of an execution slice (ES) 42AA that can be used to implement instruction execution slices ES0-ES7 in FIGS. 2-3 is shown. Inputs from the dispatch queues are received via dispatch routing network 32 by a register array 70 so that operands and the instructions can be queued in execution reservation stations (ER) 73 of issue queue 75. Register array 70 is architected to have independent register sets for independent instruction streams or where execution slice 42AA is joined in a super-slice executing multiple portions of an SIMD instruction, while dependent register sets that are clones in super-slices are architected for instances where the super-slice is executing non-SIMD instructions. An alias mapper 71 maps the values in register array 70 to any external references, such as write-back values exchanged with other slices over write-back routing network 37. A history buffer HB 76 provides restore capability for register targets of instructions executed by ES 42AA. Registers may be copied or moved between super-slices using write-back routing network 37 in response to a mode control signal, so that the assignment of slices to a set of threads or the assignment of slices to operate in a joined manner to execute as a super-slice together with other execution slices can be reconfigured. Execution slice 42AA is illustrated alongside another execution slice 42BB to illustrate an execution interlock control 79 that may be provided between pairs of execution slices within execution slices ES0-ES7 of FIGS. 2-3 to form a super-slice, in which execution slice 42AA is configurable as a master execution slice and execution slice 42BB is configurable as a slave execution slice. Details of execution slice 42AA, execution slice 42BB and execution interlock control 79 are described below with reference to FIG. 8. Execution interlock control 79 provides for coordination between execution slices 42AA and 42BB supporting execution of a single instruction stream, including wide-instruction/vector instruction execution as described above, since otherwise execution slices ES0-ES7 independently manage execution of their corresponding instruction streams.

Execution slice 42AA includes multiple internal execution pipelines 74A-74C and 72 that support out-of-order and simultaneous execution of instructions for the instruction stream corresponding to execution slice 42AA. The instructions executed by execution pipelines 74A-74C and 72 may be internal instructions implementing portions of instructions received over dispatch routing network 32, or may be instructions received directly over dispatch routing network 32, i.e., the pipelining of the instructions may be supported by the instruction stream itself, or the decoding of instructions may be performed upstream of execution slice 42AA. Execution pipeline 72 is illustrated separately multiplexed to show that single-pipeline, multiple-pipeline or both types of execution units may be provided within execution slice 42AA. The pipelines may differ in design and function, or some or all pipelines may be identical, depending on the types of instructions that will be executed by execution slice 42AA. For example, specific pipelines may be provided for address computation, scalar or vector operations, floating-point operations, etc. Multiplexers 77A-77C provide for routing of execution results to/from history buffer 76 and routing of write-back results to write-back routing network 37, I/O routing network 39 and AGEN routing network(s) 38 that may be provided for routing specific data for sharing between slices or operations, or for load and store address and/or data sent to one or more of load-store slices LS0-LS7. Data, address and recirculation queue (DARQ) 78 holds execution results or partial results such as load/store addresses or store data that are not guaranteed to be accepted immediately by the next consuming load-store slice LS0-LS7 or execution slice ES0-ES7. The results or partial results stored in DARQ 78 may need to be sent in a future cycle, such as to one of load-store slices LS0-LS7, or to special execution units such as one of cryptographic processors 34A,34B. Data stored in DARQ 78 may then be multiplexed onto AGEN bus 38 or store data bus 39 by multiplexers 77B or 77C, respectively.

Referring now to FIG. 8, details of control logic within execution slice 42AA and execution slice 42BB that generally corresponds to execution interlock control 79 are shown in accordance with an embodiment of the invention. For simplicity, the control logic for controlling the issue of LS operations is not shown, since execution slice 42AA and execution slice 42BB are not linked/unlinked for issuing LS operations of different width. Age array 92A has two 8-bit input ports that each enable access to one of eight entries from two 8-bit output ports. For each port, age array 92A will return an index to the oldest entry for which a corresponding bit is set in the byte provided at the corresponding input port. One input to age array 92A is provided from an Allow Issue vector in a latch L1A and the other input is a FX/VS ready vector in latch L1A. At each issue cycle, the oldest entry having a bit set in the Allow Issue vector is retrieved from age array 92A and used to retrieve an FX/VS operation from reservation station 94A, which is loaded into master slice FX/VS operation latch FXMop. In the same issue cycle, the oldest entry in age array 92A having a bit set in the FX/VS ready vector is compared with the 128 b vector in latch L1A by 8-bit AND-OR logic 96, which asserts control signal overwrite if the oldest ready operation is a 128-bit operation. Control signal overwrite causes multiplexer 91A to select the output of 128-bit FX/VS ready logic 90A, which sets the Allow Issue vector in latch L1A to a bit-field representing the set of ready 128-bit FX/VS operations. The oldest entry in age array 92A having a bit set in the FX/VS ready vector is also inverted by 8-bit inverter INVM to form a mask that is provided to 8-way logical-AND gate AND2 to mask off the entry that is updated in the Allow Issue vector in latch L1A from being set in the FX/VS ready vector in latch L1A, preventing the entry retrieved from age array 92A from being set in the Allow Issue vector on a subsequent cycle. 8-way logical-OR gate OR1 merges the outputs of 128-bit FX/VS ready logic 90A and 64-bit FX/VS ready logic 90B so that all ready operations (except for the operation masked by 8-way logical-AND gate AND2) are represented in the FX/VS ready vector in latch L1A at the next issue cycle.

In execution slice 42BB, which is configured as a slave execution slice, an overwrite issue cycle is triggered by control signal overwrite being in an asserted state, effectively reserving the next issue cycle for issue of the other half of the oldest 128-bit operation, which has been set up for issue from execution slice 42AA as described above. Control signal overwrite causes a multiplexer 91B to select the output of a selector 91C that selects one of the 8-bit entries in queue position array 93 using the 1-hot read address of the oldest ready entry that is output by age array 92A. The selected entry from queue position array 93 overwrites the next Allow Issue vector in a latch L1B causing the next issue operation in slave execution slice 42BB to be the half of the 128-bit operation stored in reservation station 94B that corresponds to the 128-bit operation in master execution slice 42AA corresponding to Allow Issue vector being written into latch L1A for issuing the 128-bit operation at the next issue cycle. Independent of the above operation, master execution slice 42AA issues the next operation selected by the Allow Issue vector in latch L1A at the output of age array 92A for issue from reservation station 94A into a FX/VS operation latch L2A, and slave execution slice 42BB issues the next operation selected by the Allow Issue vector in latch L1B at the output of age array 92B from reservation station 94B into a FX/VS operation latch L2B. The above operation issues the oldest 64-bit operation in each of master execution slice 42AA and slave execution slice 42BB until the next issue cycle after a 128-bit operation becomes the oldest ready operation in age array 92A, at which time, the mask indicating the allowed 128-bit operations has been pre-loaded into latch L1A and the index/address of the entry in age array 92B corresponding to the oldest allowed 128-bit operation 128-bit override has been loaded into latch L2B to cause the oldest allowed 128-bit operation to be issued by both master execution slice 42AA and slave execution slice 42BB in tandem.

Referring now to FIG. 9, an example of a load-store (LS) slice 44 that can be used to implement load-store slices LS0-LS7 in FIGS. 2-3 is shown. A load/store access queue (LSAQ) 80 is coupled to AGEN bus 38, and the direct connection to AGEN bus 38 and LSAQ 80 is selected by a multiplexer 81 that provides an input to a cache directory 83 of a data cache 82 in cache slice 46 via memory bus 40. The output of multiplexer 81 also provides an input to a load reorder queue (LRQ) 87 or store reorder queue (SRQ) 88 from either LSAQ 80 or from AGEN bus 38, or to other execution facilities within load-store slice 44 that are not shown. Load-store slice 44 may include one or more instances of a load-store unit that execute load-store operations and other related cache operations. To track execution of cache operations issued to LS slice 44, LRQ 87 and SRQ 88 contain entries for tracking the cache operations for sequential consistency and/or other attributes as required by the processor architecture. While LS slice 44 may be able to receive multiple operations per cycle from one or more of execution slices ES0-ES7 over AGEN bus 38, all of the accesses may not be concurrently executable in a given execution cycle due to limitations of LS slice 44. Under such conditions, LSAQ 80 stores entries corresponding to as yet un-executed operations. SRQ 88 receives data for store operations from store data bus 39, which are paired with operation information such as the computed store address. As operations execute, hazards may be encountered in the load-store pipe formed by LS slice 44 and cache slice 46, such as cache miss, address translation faults, cache read/write conflicts, missing data, or other faults which require the execution of such operations to be delayed or retried. In some embodiments, LRQ 87 and SRQ 88 are configured to re-issue the operations into the load-store pipeline for execution, providing operation independent of the control and operation of execution slices ES0-ES7. Such an arrangement frees resources in execution slices ES0-ES7 as soon as one or more of load-store slices LS0-LS7 has received the operations and/or data on which the resource de-allocation is conditioned. LSAQ 80 may free resources as soon as operations are executed or once entries for the operations and/or data have been stored in LRQ 87 or SRQ 88. Control logic within LS slice 44 communicates with DARQ 78 in the particular execution slice ES0-ES7 issuing the load/store operation(s) to coordinate the acceptance of operands, addresses and data. Connections to other load-store slices are provided by AGEN bus 38 and by write-back routing network 37, which is coupled to receive data from data cache 82 of cache slice 46 and to provide data to a data un-alignment block 84 of a another slice. A data formatting unit 85 couples cache slice 44 to write-back routing network 37 via a buffer 86, so that write-back results can be written through from one execution slice to the resources of another execution slice. Data cache 82 of cache slice 46 is also coupled to I/O routing network 41 for loading values from higher-order cache/system memory and for flushing or casting-out values from data cache 82. In the examples given in this disclosure, it is understood that the instructions dispatched to instruction execution slices ES0-ES7 may be full external instructions or portions of external instructions, i.e., decoded “internal instructions.” Further, in a given cycle, the number of internal instructions dispatched to any of instruction execution slices ES0-ES7 may be greater than one and not every one of instruction execution slices ES0-ES7 will necessarily receive an internal instruction in a given cycle.

While the invention has been particularly shown and described with reference to the preferred embodiments thereof, it will be understood by those skilled in the art that the foregoing and other changes in form, and details may be made therein without departing from the spirit and scope of the invention. 

What is claimed is:
 1. A method of executing program instructions by a processor core, the method comprising: receiving instructions of a first instruction stream at a master execution slice having a first issue queue; receiving instructions of a second instruction stream and instructions of the first instruction stream that require a greater execution width greater than a lesser width of the master execution slice and the slave execution slice at a slave execution slice having a second issue queue; detecting when a first instruction of the first instruction stream has the greater width; and responsive to detecting that the first instruction has the greater width, controlling the slave execution slice to reserve a first issue cycle for issuing the first instruction in parallel across the master execution slice and the slave execution slice with a control logic.
 2. The method of claim 1, further comprising: reserving the first issue cycle during an earlier issue cycle of the slave execution slice; issuing an instruction of the second instruction stream from the slave execution slice while the control logic has reserved the first issue cycle; and at a subsequent issue cycle, issuing the first instruction in parallel across the master execution slice and the slave execution slice.
 3. The method of claim 2, further comprising: responsive to detecting that the first instruction of the first instruction stream has the greater width, setting an allow bit corresponding to an issue queue entry of the first instruction that indicates that the first instruction is allowed for issue; and issuing a corresponding portion of the first instruction in response to detecting that the allow bit is set at a next issue cycle.
 4. The method of claim 3, wherein the master execution slice comprises a first age array for storing first indications of a first sequence in which instructions of the first instruction stream that have been dispatched to the master execution slice but not yet issued, wherein the method further comprises: retrieving an entry from the first age array corresponding to an oldest instruction present in the first age array that is ready for issue; and comparing the retrieved entry to a mask indicating which entries have the greater width, wherein the first instruction of the first instruction stream is the oldest instruction present in the first age array, whereby the control logic detects that the first instruction of the first instruction stream has the greater width.
 5. The method of claim 4, wherein the slave execution slice comprises a second age array for storing second indications of a second sequence in which instructions of the second instruction stream that have been dispatched to the slave execution slice but not yet issued, wherein the method further comprises: at issue cycles, retrieving an oldest allowed entry of the first age array and an oldest allowed entry of the second age array; and using the retrieved entries to issue corresponding instructions for execution by the master execution slice the slave execution slice.
 6. The method of claim 5, further comprising responsive to detecting that the first instruction of the first instruction stream has the greater width, overwriting a bit field indicating allowed entries in the second age array to a value specifying a portion of the first instruction corresponding to the slave execution slice to be issued by the slave execution slice at a next execution cycle. 